Notes/Domino 6 and 7 Forum : Yet more info...

The diiop.exe certainly has the TCPNameAndPwd field in the binary (naughty, I know..).

Various attempts at setting this field failed - all giving the same results.

(I tried setting the field to "0", 1, "Yes", 0, etc).

I've also tried setting the HTTP_EnableSessionAuth to "0", "1", and "2" to no avail (with TCPNameAndPwd = "1").

Looks like DIIOP is ignoring whatever results it gets back from this field.

Setting DIIOP_DEBUG_CONFIG=1 gets this on startup (for this site).

Config> Type == 'WebSite'
Config> WSHostingSrvrs == '*'
Config> WSHostingSrvrs == '1'
Config> ISiteOrg == 'BCS'
Config> WSHTMLDir == 'domino\html'
Config> WSJVADR == 'domino\java'
Config> WSIsDflt == '0'
Config> HTTP_EnableSessionAuth == '0'
Config> HTTP_SSOCfg == ''

Oddly enough, its reporting that HTTP_EnableSessionAuth = "0", even though its been set to "1". I'm guessing that since the TCPNameAndPwd fields arent there, then it relies on the EnableSessionAuth being set to true before the TCPNameAndPwd field gets looked at. Perhaps this is a good place to start ?

Can some nice DIIOP application developer have a quick look at the source and confirm ? And perhaps suggest a workaround ?

Thanks again

[I have to re-iterate. This is ALL on the pre-release - August 2002 - code base. This problem may NOT exist on the release code. Okay - this post shouldnt really be in this forum - but as its going to take a week to get the release code - I might as well get to the bottom of this mystery. It might exist in Gold. ]

Cheers,

--* Bill

Notes/Domino 6 and 7 Forum

Document Options

Search this forum

Forum views and search

Member Tools

RSS Feeds